Skip to main content

Create a user using REST

To create users using the Bizagi SCIM you must use the service described in this article. The following example uses POSTMAN as the client, but you are able to invoke this service from any client compatible with RESTful services with OAuth 2.0 authentication.

Before continue, review the Getting started with the synchronization procedure section.

Resource URL
[Project_URL]/scim/v2/Users

HTTP Method
POST

Authorization
OAuth 2.0

Input
The structure of the JSON message that must be sent in the body of the invocation is the following. In [VariableName] you find the name of variables that must be sent from your external system:

{
"schemas":[
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"userName":"[userName]@[domain]",
"active":"[activeUser]",
"name":{
"familyName":"[FamilyName]",
"middleName":"[MiddleName]",
"givenName":"[GivenName]"
},
"emails":[
{
"value":"[email]",
"type":"[emailType]",
"primary":"[primaryEmail]"
}
],
"phoneNumbers":[
{
"value":"[phoneNumber]",
"type":"[phoneType]",
"primary":"[primaryPhone]"
}
],
"urn:ietf:params:scim:schemas:extension:bizagi:2.0:UserProperties":
{
"DelegateEnabled": [DelegateEnabled],
"enabledForAssignation": [AssignationEnabled],
"createdCasesSkipAssigRules": [SkipAssignations]
"[NewUserProperty]": [PropertyValue]
}
}

Note:
Synchronization of User Properties is not available in Azure AD.

Where

Variable XPathDescriptionTypeBizagi User Property (WFuser)
userNameThe userName in Bizagi. This is a mandatory field. Username@domain cannot exceed 25 characters. You can also use this format domain\user.StringuserName and domain
activeBoolean value that defines if the user is active in Bizagi an can access the Work Portal.BooleanActive
name.FamilyNameLast name of the user. This is concatenated with the GivenName and MiddleName, and sent as the name of the user in this format "givenName_MiddleName_FamilyName". This is a mandatory field if the others are empty.Stringname = GivenName_MiddleName_FamilyName
name.MiddleNameMiddle name of the user. This is concatenated with the GivenName and FamilyName and sent as the name of the user in this format "givenName_MiddleName_FamilyName". This is a mandatory field if the others are empty.Stringname = GivenName_MiddleName_FamilyName
name.GivenNameFirst name of the user. This is concatenated with the MiddleName and FamilyName, and sent as the name of the user in this format "givenName_MiddleName_FamilyName". This is a mandatory field if the others are empty.Stringname = GivenName_MiddleName_FamilyName
emails.valueE-mail of the user in Bizagi.StringContact email
emails.TypeOnly the work type is stored in Bizagi. The type of email is not stored in the WFUser, but this parameter must have a value in the JSON.StringN/A
emails.primaryBoolean value. Must always be true if you want to store the email in Bizagi.BooleanN/A
phoneNumbers.valueThe mobile phone number stored in Bizagi.StringContact Cellphone
phoneNumbers.TypeOnly the work type is stored in Bizagi. The type of phone is not stored in the WFUser, but this parameter must have a value in the JSON.StringN/A
phoneNumbers.primaryBoolean value. Must always be true if you want to store the phone number in Bizagi.BooleanN/A
DelegateEnabledBoolean value that defines if the user is going to have a delegated user.BooleanDelegate Enabled
enabledForAssignationBoolean value that defines if the user can be selected by the administrator in assignments.BooleanEnabled for Assignation
createdCasesSkipAssigRulesBoolean value that defines if cases created by the user skip assignment.BooleanSkip assignments on cases created by me
NewUserPropertyThis is an example of a new user property created in the expert view. This is not supported in Azure AD.Same as the new user propertyNew user property

The final execution in POSTMAN looks like this:

SCIM_10

The response is a JSON with the SCIM schema and the information saved in Bizagi.

Note:
You cannot create multiple users in the same invocation. A bulk method to create multiple users is not available.